mgmt, monitor, prepare beta SDK for upgrade of metricAlert_API.json 2024-03-01-preview#47160
Merged
weidongxu-microsoft merged 9 commits intoAzure:mainfrom Nov 6, 2025
Merged
Conversation
Contributor
API Change CheckAPIView identified API level changes in this PR and created the following API reviews |
9846189 to
4bb1681
Compare
XiaofeiCao
approved these changes
Nov 6, 2025
Member
Author
|
/check-enforcer override |
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR prepares the Azure Monitor SDK for an upgrade to the metricAlert_API.json 2024-03-01-preview specification. The changes introduce new data source types, identity management capabilities, and expanded alert criteria options including PromQL support.
Key Changes:
- Added support for PromQL-based metric alerts with
PromQLCriteria,MultiPromQLCriteria, and related classes - Introduced managed identity support with new
Identity,ManagedServiceIdentity, andUserAssignedIdentityclasses - Added new data source types including OpenTelemetry (metrics, logs, traces), ETW providers, Event Hub, and platform telemetry
- Enhanced data collection rules with enrichment capabilities, failover configuration, and ingestion quotas
- Updated existing models with additional properties and improved documentation
Reviewed Changes
Copilot reviewed 187 out of 215 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| PromQLCriteria.java | Implements PromQL-based alert criteria with failing periods configuration |
| QueryFailingPeriods.java | Defines time-based alert activation configuration using ISO 8601 duration |
| MultiPromQLCriteria.java | Base class for PromQL criteria with discriminator pattern support |
| Identity.java | Resource identity management with user-assigned identity support |
| ManagedServiceIdentity.java | System and user-assigned identity configuration |
| OtelTracesDataSource.java, OtelMetricsDataSource.java, OtelLogsDataSource.java | OpenTelemetry data collection support with enrichment and routing |
| EtwProviderDataSource.java | ETW provider configuration for Windows event collection |
| EventHubDataSource.java, EventHubDestination.java | Event Hub integration for data ingestion and output |
| EnrichmentData.java, StorageBlob.java | Data enrichment from Azure Storage blobs |
| FailoverConfigurationSpec.java | Multi-region failover support for data collection |
| IngestionQuotas.java | Rate limiting configuration for data ingestion |
| MetricAlertResourcePatch.java | Enhanced with identity, custom properties, and resolve configuration |
| Various enum classes | New extensible enums for data source streams, provisioning states, and log levels |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
specs at Azure/azure-rest-api-specs#38616
service confirmed that rollout is done.
Description
Please add an informative description that covers that changes made by the pull request and link all relevant issues.
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:
General Guidelines and Best Practices
Testing Guidelines